I guess Ii's supposed to be configured on CI, here is the place only for some placeholder

cc @igordmn

It is better to configure it only here, not on CI.

Because it is a dependency version, not a version of the building component.

It is usually better to define such versions in lib.versions.toml, not in gradle.properties

I have to have a place for version declaration that I can use in build script as well as in tests. I can't use lib.versions.toml from tests. I see that versions are exported to sources via ComposeBuildConfig generation. And ComposeBuildConfig is generated based on gradle.properties. Though I can use lib.versions.toml from build.gradle.kts and export it via ComposeBuildConfig but, I am not sure here because it won't be aligned with other declarations.

Though I can use lib.versions.toml from build.gradle.kts and export it via ComposeBuildConfig but, I am not sure here because it won't be aligned with other declarations.

It is not so important, but I suggested this because of the different nature from the build perspective - HotReload is hardcoded dependency that is built separately, Compose/Material3 on the other hand are non-hardcoded components passed from CI. That is why, it is probably better to have them configured differently.

From user (not build) perspective, they probably have the same nature - they are all versions of something provided by the plugin. That is why, it is probably better to have them in one place in ComposeBuildConfig.

The edge between component/dependency and hardcoded/passed from CI is thin, so any solution in the end should work, choose one you think is better.